NOTE - THIS IS BETA SOFTWARE AND WILL EXPIRE ON AUGUST 16, 1996. IT IS INTENDED FOR TESTING BY FOLKS THAT HAVE EXPERIENCED PROBLEMS WITH FreePPP 2.5rf. UNLESS YOU ARE REALLY EXPERIENCING ONE OF THE PROBLEMS ADDRESSED IN THIS BETA YOU SHOULD PROBABLY WAIT UNTIL THE FINAL RELEASE OF FreePPP 2.5v2 IS AVAILABLE BEFORE UPDATING. IT SHOULD BE AVAILABLE BY AUGUST 3rd IN THE USUAL LOCATIONS.
NOTE - <ftp://members.aol.com/freepppgrp/> is now the 'official' home for test versions of FreePPP. Release versions will also appear here in addition to being submitted to MacGifts for the InfoMac and UMich archives. DO NOT SEND E-MAIL TO THIS AOL ACCOUNT - IT WILL BE DELETED WITHOUT BEING READ!
The password for the accompanying FreePPP2.5v2b5.sea archive is 'mongo' (no quotes, all lower case). DO NOT POST THIS PASSWORD IN A PUBLIC FORUM! IT'S HIDING IN THIS READ ME SO FOLKS WILL BE FORCED TO READ THIS BLINKIN' READ ME!
How to report problems:
Use a subject containing the words 'FreePPP 2.5v2 Beta Report' (which will allow my filter in Eudora to funnel all reports to a single mailbox automatically) and send reports to sdagley@iu.net. NOTE - Messages with other subject headings will usually be ignored. If it's a crashing problem please send a Macsbug log file. You might also send a list of the other Extensions and Control Panels you have installed. NOTE - Now Utilities Profile users DO NOT send me a list of every application and font you have installed. Do not send me log files without some sort of descriptive name and text in the file itself describing why you sent it. You should also be using Macsbug 6.5.3 which can be found somewhere on Apple's ftp.support.apple.com site. Once you are in Macsbug and ready to generate a log file type in something similiar to the following (but without the quotes 'stdloginto freepppcrash8500'. This invokes the stdloginto macro and tells it to save the log into the file named 'freepppcrash8500'. You would of course substitute a different name for your report.
Open Transport 1.1 and 68K Mac Warning:
There have been several reports of crashes on 68K Macs when using Open Transport 1.1, part of the recent System 7.5 Update 2.0/System 7.5.3 upgrade, and quitting an Internet app. This was initially blamed on RAM Doubler but Connectix and others have verified the problem occurs even without RAM Doubler. At this time we recommend you not use Open Transport 1.1 on a 68K based Mac as the problem does not occur when using MacTCP. Use the Network Software Selector application in the Apple Extras folder and switch to Classic Networking to re-enable MacTCP.
Things known or thought to be wrong in 2.5v2b6:
It's been reported that FreePPP will sometimes crash if it brings up the Retry/Cancel alert when there is a problem connecting. It apparently happens most often when using Emailer 1.1v2. We've received a couple of additional reports that this occurs with other apps also but haven't found the culprit yet (of course it never happens to me).
The scroll bar for the Account or Location lists does not update properly if you delete entries from the end of the list. This is only a visual bug and the un-displayed accounts can be selected from the Connect to: popup which will force the scrolling list to update.
PC Card modems in PowerBooks might not respond if the system has been shutdown or re-started. If you encounter this problems _please_ report it as I have not been able to consistently reproduce it so I don't know it it might actually be a fault in my PowerBook or modem.
Fixed/New in 2.5v2b6:
Just one change but it's a biggie...
Rick Reynolds (with help the folks at Global Village) - Put in a fix for the GV menu bar modem status indicator. There is no longer an option to turn this mod on or off as it should not cause any problems (unlike the 'fix' in 2.5v2b5).
Fixed/New in 2.5v2b5:
Alec Carlson - Improved the handling of the dialing and hangup phases - should now close connections faster and better handle getting the modem's attention prior to dialing.
Improved handling of clicks in the Tab controls - should now swich tabs for folks that click faster than a politician changes their position. This fix should also take care of the occasional weird hiliting of the tabs when the window is first expanded.
THIS CHANGE IS NOW OBSOLETE - Added new setting in the Modem Config... dialog for working around a bug in Global Village's software that displays the modem status in the menu bar. NOTE - this fix may have side effects and it's recommended that you not use it unless you actually are using the status bar display software.
Actually implemented the connect script code changes alluded to below but missing from 2.5v2b4.
Fixed/New in 2.5v2b4:
Tweaked the connect script code again.
Rick Reynolds - Changed the way data is buffered for xmit which should improve performance, especially for RealAudio users. This change may have adverse effect for some apps but we haven't seen any such examples. If you experience problems you think are related to this please let me know ASAP.
No longer display connection messages from server when connection with CHAP or PAP authentication - regardless of the setting of the "Show alerts during connect and disconnect" option. If you really miss the "Login Succesful" alert this prevents please let me know.
Increased the memory allocation for FreePPP Setup to workaround a prefs corruption problem in low memory situations.
Fixed/New in 2.5v2b3:
Scripted connections should now work with 'verbose' terminal servers that spew lots of unnecessary (since you never see it) verbage during a login session.
Joe Husk - Fixed problem where providing prompts for the name and password dislog would overflow an internal buffer.
The problem with crashing when an app other than FreePPP Setup initiates a connection should be fixed. This same fix should eliminate the problem with trying to re-connect after closing a connection would crash.
Now properly handle multi-number ISDN calls when applying the Location logic for area codes.
The number that will be dialed for the selected account is now displayed in FreePPP Setup. This will allow you to verify that you have properly configured the Account and Location settings to dial the number you want without having to actually initiate a call.
